Method and apparatus for providing media resources in a communication network

ABSTRACT

Aspects of the subject disclosure may include, for example, providing a request associated with a call session to a server, wherein the request includes capability information associated with user equipment. A codec is identified according to the capability information to obtain an identified codec, which facilitates media service to the user equipment. The media service is accessed from a media resource function, which in turn, is accessed by the server responsive to the identified codec. An operable resource identifier is identified responsive to a search of a codec table, wherein the server accesses the operable resource identifier associated with the media resource function from a domain name server responsive to the resource identifier not being available at the codec table. Other embodiments are disclosed.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/751,721 filed on Jan. 24, 2020, which is a continuation of U.S.patent application Ser. No. 16/052,678 filed on Aug. 2, 2018, now U.S.Pat. No. 10,581,930, which is a continuation of U.S. patent applicationSer. No. 15/446,122 filed on Mar. 1, 2017, now U.S. Pat. No. 10,069,875.All sections of the aforementioned application(s) and/or patent(s) areincorporated herein by reference in their entirety.

FIELD OF THE DISCLOSURE

The subject disclosure relates to a method and apparatus for providingmedia resources in a communication network.

BACKGROUND

Modern telecommunications systems provide consumers with telephonycapabilities while accessing a large variety of content. Consumers areno longer bound to specific locations when communicating with others orwhen enjoying multimedia content or accessing the varied resourcesavailable via the Internet. Network capabilities have expanded and havecreated additional interconnections and new opportunities for usingmobile communication devices in a variety of situations. Intelligentdevices offer new means for experiencing network interactions in waysthat anticipate consumer desires and provide solutions to problems.

BRIEF DESCRIPTION OF THE DRAWINGS

Reference will now be made to the accompanying drawings, which are notnecessarily drawn to scale, and wherein:

FIG. 1 depicts an illustrative embodiment of a system that can beutilized for providing media resources to user equipment in acommunication network;

FIG. 2 depicts an illustrative embodiment of a method used in portionsof the system described in FIG. 1;

FIG. 3 depicts illustrative embodiments of a communication system thatprovide media services for use by the system of FIG. 1;

FIG. 4 depicts an illustrative embodiment of a web portal forinteracting with the communication systems of FIGS. 1 and 3;

FIG. 5 depicts an illustrative embodiment of a communication device; and

FIG. 6 is a diagrammatic representation of a machine in the form of acomputer system within which a set of instructions, when executed, maycause the machine to perform any one or more of the methods describedherein.

DETAILED DESCRIPTION

The subject disclosure describes, among other things, illustrativeembodiments for providing a Media Resource Function (MRF) to supportIP-based multimedia services for call sessions in a communicationsystem, such as a Long-Term Evolution (LTE) system. Voice-over-LTE(VoLTE), Video-over-LTE (ViLTE), or video streaming services may use MRFservices that provide processing of real-time audio and/or video streamswithin IP-based communication networks, such as an IP MultimediaSubsystems (IMS).

An Application Server (AS) can receive a transport protocol messageassociated with a call session and can determine if the transportprotocol message includes session attributes and media descriptioninformation. The AS can determine an optimal codec required forproviding media services to a communication device involved in the callsession. The AS can access a database that associates available codecswith resource identifiers of known MRF services available within the IMSsystem. If a resource identifier for a MRF service including the neededcodec is not found, then the AS can query a Domain Name Server (DNS) toobtain the resource identifier. The AS can then use the resourceidentifier to transmit a request to the MRF service to provide mediaservices to the communication device. Other embodiments are described inthe subject disclosure.

One or more aspects of the subject disclosure include a method, caninclude receiving, by a processing system including a processor, atransport protocol message associated with user equipment associatedwith a call session, and, in turn, detecting, by the processing system,session description protocol information in a header of the transportprotocol message. The method can also include determining, by theprocessing system, a session attribute from the session descriptionprotocol information, and, in turn, determining, by the processingsystem, a media description from the session description protocolinformation. The session attribute can include capability informationassociated with the user equipment. The method can include determining,by the processing system, a first codec to provide a first media serviceto the user equipment associated with the call session according to thesession attribute and the media description. Responsive to determiningthe first codec, the method can include searching, by the processingsystem, a codec table to obtain a first resource identifier associatedwith a first media resource function to provide the first media serviceaccording to the first codec and, in turn, transmitting, by theprocessing system, a first request to the first media resource functionto provide the first media service to the user equipment associated withthe call session. If the first resource identifier associated with thefirst codec is not available at the codec table, then the method caninclude accessing, by the processing system, the first resourceidentifier associated with the first media resource function from adomain name server.

One or more aspects of the subject disclosure include a machine-readablestorage medium, including executable instructions that, when executed bya processing system including a processor, facilitate performance ofoperations, including receiving a transport protocol message associatedwith user equipment associated with a call session, determining asession attribute and a media description from the transport protocolmessage, and determining a first codec to provide a first media serviceto the user equipment associated with the call session according to thesession attribute and the media description. The session attribute caninclude capability information associated with the user equipment.Responsive to determining the first codec, the operations can includesearching a codec table to obtain a first resource identifier associatedwith a first media resource function to provide the first media serviceaccording to the first codec and, in turn, transmitting a first requestto the first media resource function to provide the first media serviceto the user equipment associated with the call session. If the firstresource identifier associated with the first codec is not available atthe codec table, then the operations can also include accessing thefirst resource identifier associated with the first media resourcefunction from a domain name server.

One or more aspects of the subject disclosure include a device includinga processing system including a processor, and a memory that storesexecutable instructions that, when executed by the processing system,facilitate performance of operations. The processing system, responsiveto executing the executable instruction, can perform operations fordetermining from a transport protocol message, capability informationassociated with user equipment associated with a call session anddetermining a first codec to provide a first media service to the userequipment associated with the call session according to the capabilityinformation. Responsive to determining the first codec, the operationscan include searching a codec table to obtain a first resourceidentifier associated with a first media resource function to providethe first media service according to the first codec and, in turn,transmitting a first request to the first media resource function toprovide the first media service to the user equipment associated withthe call session. If the first resource identifier associated with thefirst codec is not available at the codec table, the operations can alsoinclude accessing the first resource identifier associated with thefirst media resource function from a domain name server.

FIG. 1 depicts an illustrative embodiment of a system that can beutilized for providing media services for call sessions and devices.FIG. 2 depicts illustrative embodiments of a method for providing mediaservices. In one embodiment, the system 100 can incorporate asubscription telecommunications service. For example, the subscriptiontelecommunications service can provide communication connectivity fortelephony devices, including mobile communication devices 116. Inanother embodiment, the system 100 can include network connectivitybetween an Internet IP network 165, an IP Multimedia Subsystem (IMS)network 155, and/or an IP Television (IPTV) network. The system 100 canprovide a content-rich communications platform that can include cable,satellite, fiber optic, and/or DSL based media content delivery systems.Available content can be any type of content, such as broadcasttelevision, cable or premium television, video on demand, or pay-per-perview television. The content can be software content, including entiresoftware programs, upgrades to programs, and/or additions to programs.Content can be subscription-based, such as basic cable, premium cable,or movie channel content. The content can be non-subscription-based,such as “free” Internet-based content of over-the-air television contentand/or single offers or purchases of content.

In one embodiment, the system 100 can provide IP-based communicationsservices, such as Voice-over-LTE (VoLTE) and/or Video-over-LTE (ViLTE).These voice and video delivery systems can combine traditional voicetelephony services with rich media content, including video streamingservices. In one embodiment, the system 100 can provide VoLTE and ViLTEservices via Application Servers (AS) 130. The AS 130 provide a richvariety of applications for use by smart devices, such as mobilecommunication devices 116. In one example, a mobile communication device116 can access the system 100 via a wireless mobility network 117 toinitiate a VoLTE calling session to another mobile communication device116. Initiation of a calling session can cause a Session InitiationProtocol (SIP) message to be generated at the IMS network 155. The SIPmessage can include information necessary for initiating the callsession, including identifiers for the calling and receiving devices116, which can be used by the IMS network 155 for initiating and routingthe call between the mobile communication devices 116. The mobilitynetwork 117 can route content to a mobile communication device 116, suchas a wireless smart phone, via a cellular, long term evolution (LTE),third generation (3G), and/or fourth generation (4G) wireless networks.In one embodiment, the mobile communication device 116 can route contentthat is received over the mobility network 117 by, for example, a mobilehotspot Wi-Fi link between the mobile communication device 116 and acomputer device 116 or a media device 108.

In one or more embodiments, the IMS network 115 can determine, from theSIP message, that the calling device 116 is requesting a VoLTE or ViLTEcall and can select an Application Server 130 for servicing the audioand/or video components of the call. To handle IP-based voice and/orvideo calls, the Application Server 130 may need to invoke one or moreMedia Resource Functions (MRF) 140-144 to provide media relatedfunctions necessary to the calling session. For example, a VoLTE orViLTE call session may require media manipulation, such as mixing voiceand/or video streams and/or producing audio tones and announcements.

In one or more embodiments, each of the MRF servers 140-144 can includeone or more codecs, or coder-encoder technology for processing datastreams. When data streams are transmitted over networks, data istypically encoded into a format suitable for efficient and reliable datatransfer and, then, decoded after it has been transferred. Many codectypes are available, each tailored to specific limitations present atthe device and network level. Codecs are implemented as a combination ofdevice hardware and software and are typically reconfigurable, so that aparticular device, such as a MRF server 140, can service more than onecodec. However, for the sake of efficiency and cost, MRF servers 140-144will typically only include a subset of the possible codecs that couldbe used. To further complicate the issue, the user equipment devices,such as the mobile communication devices 116, are often very withrespect to codec types due to the hardware, software, and wirelessnetworking constraints faced by the these devices.

If an Application Server 130 invokes a MRF server 140 without knowledgeof relationships between the codec capabilities of an end user device,such as a mobile communication device 116, and the codec capabilities ofthe MRF server 140, then the Application Server 130 may selectcombinations of data streams that mismatch with the MRF sever 140 and/ormobile communication device 116. Further, with each MRF server 140selected, the Application Server 130 may be required to seek help from aDNS to obtain the address of what, ultimately, may turn out to be thewrong MRF server 140. In this scenario, the Application Server 130 maybe required to perform a “trial and error” process of selecting anddeselecting the MRF server 140 and/or codec until a correctly performingcodec/media stream/communication device 116 is found. This approach cancreate a delay in processing VoLTE/ViLTE calls, sometimes in a range ofmany seconds, which can result in delayed call control setup and/orextreme poor quality especially in ViLTE sessions. This approach canreduce customer satisfaction, while increasing churn rate and customerdissatisfaction.

In one or more embodiments, the IMS network 155 can send a transportprotocol message to the Application Server 130. The Application Server130 can receive the transport protocol message in step 204. Thetransport protocol message can be associated with a call session, suchas a VoLTE or ViLTE session. The transport protocol message can beassociated with a data streaming event, such as a request for contentfrom a mobile communication device 116. The transport protocol messagecan be a SIP message. The transport protocol message can includeinformation describing requirements or capabilities that are needed forsuccessful provision of service to the requesting device. For example,the transport protocol message can include SIP header information thataids the Application Server 130 in selecting a MRF server 140 that meetscodec requirements or that is best or most appropriate for providingresources needed for providing media services. The transport protocolmessage can include header information as well as payload information.

In one or more embodiments, the Application Server 130 can examineheader information, such as Session Description Protocol (SDP)information in the transport protocol message, to detect sessionprotocol information in step 208. The SDP information can include any ofseveral types of media attributes and parameters that can be subject toan industry standard. In various embodiments, the SDP information can beincluded in a header of a SIP message and can include descriptions forthe type of media (e.g., video, audio), the transport protocol (e.g.,RTP/UDP/IP, H.320), the format of the data (e.g., H.261, video, MPEGvideo). Generally, the SDP header, or SDP session description, caninclude a series of descriptive items that can be in the general formatof <type>=<value>. For example, one SDP session record can include arecord, “s=SDP Seminar,” where “s” is a description type for a “sessionname,” and “SDP Seminar” is the particular value associated with thissession name. In this case, the record, “s=SDP Seminar,” tells thereceiving Application Server 130 that the current session name is “SDPSeminar.”

The SDP header can include a series of records of this type that canprovide information defining the session. Two other particulardescriptive items that may illustratively be used, separately ortogether, to define the codec requirements for a session are the type“m” for “media” records and the type “a” for attributes. The type “m”session record can specify the media type, port, number of ports,transport protocol, and format of the session. For example, the “m”record could read, “m=video 49170/2 RTP/AVP 31.” This “m” record wouldtell the Application Server 130 that the current session includes mediathat is in the form of video that is received on ports 49170 and 49171as a first RTP.RTCP pair on ports 49172 and 49173 as a second RTP.RTCPpair, where the transport protocol is RTP/AVP and the format “31” isused. The type “a” session record can specify various attributes. The“a” type record can include variable lengths of data depending on theparticular type of attribute. In addition, the “a” record can becontextual, such that its meaning depends, in part, upon other records,such as the “m” record. For example, the “a” record can be directed tothe attribute, “rtpmap,” which can map an RTP payload type number to anencoding name denoting the payload format to be used. The “rtpmap”attribute can also provide information on clock rate and encodingparameters. For example, the “a” record could read, “rtpmap:98L16/160000/2.” This record defines a dynamic payload type that is 16-bitlinear encoded stereo sampled at 16 kHz. If the “m” record defined thecontent as including audio with RTP protocol, then the “a” record wouldtell the Application server how the payload audio data is encoded.

In one or more embodiments, the Application Server 130 can analyze thesession description information to determine one or more capabilitiesthat are required to provide media services necessary to the callsession in step 212. For example, the Application Server 130 candetermine the type of media that is being received and transmitted, itstransmission protocol, and a mapping between the transmission protocoland an encoding/decoding scheme (with specific parameters) that isneeded to make a data stream compatible with the communication device116 and the intervening network. The Application Server 130 can use thisinformation to determine a codec (encoder or decoder) that is needed forthe media service described in the transport protocol message in step216. For example, the Application Server 130 can determine that a datacompression scheme call, “PCMU” (i.e., G.711 compression is required.

In one or more embodiments, the Application Server 130 can select anappropriate MRF server 140 based on the codec that is determined. TheApplication Server 130 can search a codec table or a MRF Database 132based on the determined codec in step 220. For example, the MRF Database132 could include a listing of various codecs and their correspondingMRF servers 140-144. In one embodiment, the MRF servers 140-144 can beinclude resource identifiers that can be used to access the MRF servers140-144. The Application Server 130 can present a codec name to the MRFDatabase 132 and receive a universal resource identifier (URI) for aspecific MRF server 140 that can provide this codec for the ApplicationServer 130 to provide a service.

In one or more embodiments, the MRF Database 132 may not include aresource identifier associated with a MRF server 140 for the codec. Inthis case, the MRF Database 132 will not find a match, in step 224, andcan notify the Application Server 130 of the lack of a match. In thiscase, the Application Server 130 can query a DNS 134 for a resourceidentifier of a MRF server 140-144 that can provide codec service instep 228. The Application Server 130 can map and select the appropriateMRF server 140 based on the DNS record configuration within theApplication Server 130. Once the Application Server 130 has obtained theresource identifier for the desired MRF server 140, the ApplicationServe 130 can instruct the MRF Database to store this identifier forfuture use. The Application Server 130 can transmit a request to theselected MRF server 140 as identified by the resource identifier in step232. The request can direct the MRF server 140 to provide a mediaservice to a mobile communication device 116, such playing an audio toneor announcement or manipulating the media stream. By selecting theproper MRF server 140, without undue delay, VoLTE/ViLTE calls can beprocessed quickly, often in a range of just milliseconds (instead ofseconds), which can result in faster call control setup and betterquality service (especially in ViLTE). These features can enhancecustomer satisfaction, reduce churn rate, and increase overall customersatisfaction and retention.

In one or more embodiments, the Application Server 130 can determine, instep 236, that the SDP header includes a request for a conference, suchas a conference call or a broadcast call. In an illustrative example,the SDP header can include an “a” record that includes a type ofconference. For example, the record could read, “a=type:moderated,”which would indicate that the payload data is associated with amoderated conference call. In this case, the Application Server 130 candetermine a Media Server Markup Language (MSML) routine capable ofsupporting the type of conference, in step 240. For example, a MSMLroutine capable of supporting a “moderated” conference can be selected.In step 244, the Application Server 130 can provide the selected MSMLrouting to search the MRF Database 132. If a resource identifier for theMSML routine is not found in the MRF database, in step 248, then theApplication Server 130 can query the DNS server 134 for the resourceidentifier in step 252. The Application Server 130 can direct theselected MRF server 140 for performing the MSML routine in step 256.

FIG. 3 depicts an illustrative embodiment of a communication system 300employing an IP Multimedia Subsystem (IMS) network architecture tofacilitate the combined services of circuit-switched and packet-switchedsystems. Communication system 300 can be overlaid or operably coupledwith system 100 of FIG. 1 and communication system 300 as anotherrepresentative embodiment of communication system 300, for using headerinformation in a transport protocol message to select a MRF server forproviding a media service to user devices in an IP-based communicationsystem.

Communication system 300 can comprise a Home Subscriber Server (HSS)340, a tElephone NUmber Mapping (ENUM) server 330, and other networkelements of an IMS network 350. The IMS network 350 can establishcommunications between IMS-compliant communication devices (CDs) 301,302, Public Switched Telephone Network (PSTN) CDs 303, 305, andcombinations thereof by way of a Media Gateway Control Function (MGCF)320 coupled to a PSTN network 360. The MGCF 320 need not be used when acommunication session involves IMS CD to IMS CD communications. Acommunication session involving at least one PSTN CD may utilize theMGCF 320.

IMS CDs 301, 302 can register with the IMS network 350 by contacting aProxy Call Session Control Function (P-CSCF) which communicates with aninterrogating CSCF (I-CSCF), which in turn, communicates with a ServingCSCF (S-CSCF) to register the CDs with the HSS 340. To initiate acommunication session between CDs, an originating IMS CD 301 can submita Session Initiation Protocol (SIP INVITE) message to an originatingP-CSCF 304 which communicates with a corresponding originating S-CSCF306. The originating S-CSCF 306 can submit the SIP INVITE message to oneor more application servers (ASs) 317 that can provide a variety ofservices to IMS subscribers.

For example, the application servers 317 can be used to performoriginating call feature treatment functions on the calling party numberreceived by the originating S-CSCF 306 in the SIP INVITE message.Originating treatment functions can include determining whether thecalling party number has international calling services, call IDblocking, calling name blocking, 7-digit dialing, and/or is requestingspecial telephony features (e.g., *72 forward calls, *73 cancel callforwarding, *67 for caller ID blocking, and so on). Based on initialfilter criteria (iFCs) in a subscriber profile associated with a CD, oneor more application servers may be invoked to provide various calloriginating feature services.

Additionally, the originating S-CSCF 306 can submit queries to the ENUMsystem 330 to translate an E.164 telephone number in the SIP INVITEmessage to a SIP Uniform Resource Identifier (URI) if the terminatingcommunication device is IMS-compliant. The SIP URI can be used by anInterrogating CSCF (I-CSCF) 307 to submit a query to the HSS 340 toidentify a terminating S-CSCF 314 associated with a terminating IMS CDsuch as reference 302. Once identified, the I-CSCF 307 can submit theSIP INVITE message to the terminating S-CSCF 314. The terminating S-CSCF314 can then identify a terminating P-CSCF 316 associated with theterminating CD 302. The P-CSCF 316 may then signal the CD 302 toestablish Voice over Internet Protocol (VoIP) communication services,thereby enabling the calling and called parties to engage in voiceand/or data communications. Based on the iFCs in the subscriber profile,one or more application servers may be invoked to provide various callterminating feature services, such as call forwarding, do not disturb,music tones, simultaneous ringing, sequential ringing, etc.

In some instances the aforementioned communication process issymmetrical. Accordingly, the terms “originating” and “terminating” inFIG. 3 may be interchangeable. It is further noted that communicationsystem 300 can be adapted to support video conferencing. In addition,communication system 300 can be adapted to provide the IMS CDs 301, 302with the multimedia and Internet services.

If the terminating communication device is instead a PSTN CD such as CD303 or CD 305 (in instances where the cellular phone only supportscircuit-switched voice communications), the ENUM system 330 can respondwith an unsuccessful address resolution which can cause the originatingS-CSCF 306 to forward the call to the MGCF 320 via a Breakout GatewayControl Function (BGCF) 319. The MGCF 320 can then initiate the call tothe terminating PSTN CD over the PSTN network 360 to enable the callingand called parties to engage in voice and/or data communications.

It is further appreciated that the CDs of FIG. 3 can operate as wirelineor wireless devices. For example, the CDs of FIG. 3 can becommunicatively coupled to a cellular base station 321, a femtocell, aWiFi router, a Digital Enhanced Cordless Telecommunications (DECT) baseunit, or another suitable wireless access unit to establishcommunications with the IMS network 350 of FIG. 3. The cellular accessbase station 321 can operate according to common wireless accessprotocols such as GSM, CDMA, TDMA, UMTS, WiMax, SDR, LTE, and so on.Other present and next generation wireless network technologies can beused by one or more embodiments of the subject disclosure. Accordingly,multiple wireline and wireless communication technologies can be used bythe CDs of FIG. 3.

Cellular phones supporting LTE can support packet-switched voice andpacket-switched data communications and thus may operate asIMS-compliant mobile devices. In this embodiment, the cellular basestation 321 may communicate directly with the IMS network 350 as shownby the arrow connecting the cellular base station 321 and the P-CSCF316.

Alternative forms of a CSCF can operate in a device, system, component,or other form of centralized or distributed hardware and/or software.Indeed, a respective CSCF may be embodied as a respective CSCF systemhaving one or more computers or servers, either centralized ordistributed, where each computer or server may be configured to performor provide, in whole or in part, any method, step, or functionalitydescribed herein in accordance with a respective CSCF. Likewise, otherfunctions, servers and computers described herein, including but notlimited to, the HSS, the ENUM server, the BGCF, and the MGCF, can beembodied in a respective system having one or more computers or servers,either centralized or distributed, where each computer or server may beconfigured to perform or provide, in whole or in part, any method, step,or functionality described herein in accordance with a respectivefunction, server, or computer.

The Application Server 130 of FIG. 3 can be operably coupled tocommunication system 300 for purposes similar to those described above.Application Server 130 can perform function 362 and thereby providemedia services to the CDs 301, 302, 303 and 305 of FIG. 3 similar to thefunctions described for Application Server 130 of FIG. 1 in accordancewith method 200 of FIG. 2. CDs 301, 302, 303 and 305, which can beadapted with software to perform function 372 to utilize the services ofthe Application Server 130 similar to the functions described forcommunication devices 116 of FIG. 1 in accordance with method 200 ofFIG. 2. Application Server 130 can be an integral part of theapplication server(s) 517 performing function 374, which can besubstantially similar to function 362 and adapted to the operations ofthe IMS network 350.

In one illustrative example, the Application Server 130 can be used toprovide a High Definition (HD) voice announcement to a VoLTE user via anAdaptive Multi-Rate Wideband codec (AMR WB). In this case, theApplication Server 130 needs to play an announcement to the end user aspart of the application logic. For example, a terminating user numberhas moved, did not pay the bill, or so forth. The Application Server 130can examine the SDP header of an incoming SIP message to check the audiocapabilities of the mobile communication device 116. The ApplicationServer 130 can select a MRF server 144, via third party call control(3PCC), which has HD voice capacity (via AMR-WB codec) to play the HDvoice announcement to the terminating party. The Application Server 130can select the MRF server 144 according to the following SIP (signaling)path:

-   -   UE←→P-CSCF(SBC)←→S-CSCF←→AS←→MRF (A).        The selected MRF 144 can provide the media service to the        communication device 116 according to the following media        (bearer) path:    -   UE←SBC←MRF(A).

In another illustrative example, the Application Server 130 can be usedto provide media services to a communication device 116 that only has aSpeex codec, with an audio compression format designed for speech andVoIP applications and podcasts. In this case, the Application Server 130can select a MRF server 142 by selecting the “others” codec in the MRFDatabase 132 and can use the Fully Qualifed Domain Name (FQDN) foraddressing the MRF server 142. The Application Server 130 can select theMRF server 144 according to the following SIP (signaling) path:

-   -   UE←→P-CSCF(SBC)←→S-CSCF←→AS←→MRF (C).        The selected MRF 144 can provide the media service to the        communication device 116 according to the following media        (bearer) path:    -   UE←SBC←MRF(C).

For illustration purposes only, the terms S-CSCF, P-CSCF, I-CSCF, and soon, can be server devices, but may be referred to in the subjectdisclosure without the word “server.” It is also understood that anyform of a CSCF server can operate in a device, system, component, orother form of centralized or distributed hardware and software. It isfurther noted that these terms and other terms such as DIAMETER commandsare terms can include features, methodologies, and/or fields that may bedescribed in whole or in part by standards bodies such as 3^(rd)Generation Partnership Project (3GPP). It is further noted that some orall embodiments of the subject disclosure may in whole or in partmodify, supplement, or otherwise supersede final or proposed standardspublished and promulgated by 3GPP.

FIG. 4 depicts an illustrative embodiment of a web portal 402 of acommunication system 400. Communication system 400 can be overlaid oroperably coupled with systems 100 of FIG. 1, and/or communication system300 as another representative embodiment of systems 100 of FIG. 1 and/orcommunication system 300. The web portal 402 can be used for managingservices of system 100 of FIG. 1 and communication system 300. A webpage of the web portal 402 can be accessed by a Uniform Resource Locator(URL) with an Internet browser using an Internet-capable communicationdevice such as those described in FIG. 1 and FIG. 3. The web portal 402can be configured, for example, to access a media processor and servicesmanaged thereby such as a Digital Video Recorder (DVR), a Video onDemand (VoD) catalog, an Electronic Programming Guide (EPG), or apersonal catalog (such as personal videos, pictures, audio recordings,etc.) stored at the media processor. The web portal 402 can also be usedfor provisioning IMS services described earlier, provisioning Internetservices, provisioning cellular phone services, and so on.

The web portal 402 can further be utilized to manage and provisionsoftware applications 362, and 472-474 to adapt these applications asmay be desired by subscribers and/or service providers of system 100 ofFIG. 1 and communication system 300. For instance, users of the servicesprovided by server 130 can log into their on-line accounts and provisionthe servers 130 with where a user may want to program a user profile,provide contact information to the server to enable it to communicationwith devices described in FIGS. 1 and 3, and so on. Service providerscan log onto an administrator account to provision, monitor and/ormaintain the system 100 of FIG. 1 or server 130.

FIG. 5 depicts an illustrative embodiment of a communication device 500.Communication device 500 can serve in whole or in part as anillustrative embodiment of the devices depicted in FIGS. 1 and 3 and canbe configured to perform portions of method 200 of FIG. 2.

Communication device 500 can comprise a wireline and/or wirelesstransceiver 502 (herein transceiver 502), a user interface (UI) 504, apower supply 514, a location receiver 516, a motion sensor 518, anorientation sensor 520, and a controller 506 for managing operationsthereof The transceiver 502 can support short-range or long-rangewireless access technologies such as Bluetooth®, ZigBee®, WiFi, DECT, orcellular communication technologies, just to mention a few (Bluetooth®and ZigBee® are trademarks registered by the Bluetooth® Special InterestGroup and the ZigBee® Alliance, respectively). Cellular technologies caninclude, for example, CDMA-1X, UMTS/HSDPA, GSM/GPRS, TDMA/EDGE, EV/DO,WiMAX, SDR, LTE, as well as other next generation wireless communicationtechnologies as they arise. The transceiver 502 can also be adapted tosupport circuit-switched wireline access technologies (such as PSTN),packet-switched wireline access technologies (such as TCP/IP, VoIP,etc.), and combinations thereof

The UI 504 can include a depressible or touch-sensitive keypad 508 witha navigation mechanism such as a roller ball, a joystick, a mouse, or anavigation disk for manipulating operations of the communication device500. The keypad 508 can be an integral part of a housing assembly of thecommunication device 500 or an independent device operably coupledthereto by a tethered wireline interface (such as a USB cable) or awireless interface supporting for example Bluetooth®. The keypad 508 canrepresent a numeric keypad commonly used by phones, and/or a QWERTYkeypad with alphanumeric keys. The UI 504 can further include a display510 such as monochrome or color LCD (Liquid Crystal Display), OLED(Organic Light Emitting Diode) or other suitable display technology forconveying images to an end user of the communication device 500. In anembodiment where the display 510 is touch-sensitive, a portion or all ofthe keypad 508 can be presented by way of the display 510 withnavigation features.

The display 510 can use touch screen technology to also serve as a userinterface for detecting user input. As a touch screen display, thecommunication device 500 can be adapted to present a user interface withgraphical user interface (GUI) elements that can be selected by a userwith a touch of a finger. The touch screen display 510 can be equippedwith capacitive, resistive or other forms of sensing technology todetect how much surface area of a user's finger has been placed on aportion of the touch screen display. This sensing information can beused to control the manipulation of the GUI elements or other functionsof the user interface. The display 510 can be an integral part of thehousing assembly of the communication device 500 or an independentdevice communicatively coupled thereto by a tethered wireline interface(such as a cable) or a wireless interface.

The UI 504 can also include an audio system 512 that utilizes audiotechnology for conveying low volume audio (such as audio heard inproximity of a human ear) and high volume audio (such as speakerphonefor hands free operation). The audio system 512 can further include amicrophone for receiving audible signals of an end user. The audiosystem 512 can also be used for voice recognition applications. The UI504 can further include an image sensor 513 such as a charged coupleddevice (CCD) camera for capturing still or moving images.

The power supply 514 can utilize common power management technologiessuch as replaceable and rechargeable batteries, supply regulationtechnologies, and/or charging system technologies for supplying energyto the components of the communication device 500 to facilitatelong-range or short-range portable applications. Alternatively, or incombination, the charging system can utilize external power sources suchas DC power supplied over a physical interface such as a USB port orother suitable tethering technologies.

The location receiver 516 can utilize location technology such as aglobal positioning system (GPS) receiver capable of assisted GPS foridentifying a location of the communication device 500 based on signalsgenerated by a constellation of GPS satellites, which can be used forfacilitating location services such as navigation. The motion sensor 518can utilize motion sensing technology such as an accelerometer, agyroscope, or other suitable motion sensing technology to detect motionof the communication device 500 in three-dimensional space. Theorientation sensor 520 can utilize orientation sensing technology suchas a magnetometer to detect the orientation of the communication device500 (north, south, west, and east, as well as combined orientations indegrees, minutes, or other suitable orientation metrics).

The communication device 500 can use the transceiver 502 to alsodetermine a proximity to a cellular, WiFi, Bluetooth®, or other wirelessaccess points by sensing techniques such as utilizing a received signalstrength indicator (RSSI) and/or signal time of arrival (TOA) or time offlight (TOF) measurements. The controller 506 can utilize computingtechnologies such as a microprocessor, a digital signal processor (DSP),programmable gate arrays, application specific integrated circuits,and/or a video processor with associated storage memory such as Flash,ROM, RAM, SRAM, DRAM or other storage technologies for executingcomputer instructions, controlling, and processing data supplied by theaforementioned components of the communication device 500.

Other components not shown in FIG. 5 can be used in one or moreembodiments of the subject disclosure. For instance, the communicationdevice 500 can include a reset button (not shown). The reset button canbe used to reset the controller 506 of the communication device 500. Inyet another embodiment, the communication device 500 can also include afactory default setting button positioned, for example, below a smallhole in a housing assembly of the communication device 500 to force thecommunication device 500 to re-establish factory settings. In thisembodiment, a user can use a protruding object such as a pen or paperclip tip to reach into the hole and depress the default setting button.The communication device 500 can also include a slot for adding orremoving an identity module such as a Subscriber Identity Module (SIM)card. SIM cards can be used for identifying subscriber services,executing programs, storing subscriber data, and so forth.

The communication device 500 as described herein can operate with moreor less of the circuit components shown in FIG. 5. These variantembodiments can be used in one or more embodiments of the subjectdisclosure.

The communication device 500 can be adapted to perform the functions ofdevices of FIG. 1, or the IMS CDs 301-302 and PSTN CDs 303-305 of FIG.3. It will be appreciated that the communication device 500 can alsorepresent other devices that can operate in systems of FIG. 1,communication systems 300 of FIGS. 3, such as a gaming console and amedia player. In addition, the controller 506 can be adapted in variousembodiments to perform the functions 362 and 472-574, respectively.

Upon reviewing the aforementioned embodiments, it would be evident to anartisan with ordinary skill in the art that said embodiments can bemodified, reduced, or enhanced without departing from the scope of theclaims described below. For example, the Application Server 130 canselect MRF servers 140-144 for VoIP services, such as messaging andchat. In another embodiment, the Application Server 130 can select MRFservers 140-144 for video services like DirectTV™. In one embodiment, aservice provider can charge graded levels of service based oncapabilities of the MRF server 140 that is selected. Other embodimentscan be used in the subject disclosure.

It should be understood that devices described in the exemplaryembodiments can be in communication with each other via various wirelessand/or wired methodologies. The methodologies can be links that aredescribed as coupled, connected and so forth, which can includeunidirectional and/or bidirectional communication over wireless pathsand/or wired paths that utilize one or more of various protocols ormethodologies, where the coupling and/or connection can be direct (e.g.,no intervening processing device) and/or indirect (e.g., an intermediaryprocessing device such as a router).

FIG. 6 depicts an exemplary diagrammatic representation of a machine inthe form of a computer system 600 within which a set of instructions,when executed, may cause the machine to perform any one or more of themethods described above. One or more instances of the machine canoperate, for example, as the Application Server 130, the mobilecommunication device 116, the MRF Server 140, the MRF Database 132, andother devices of FIGS. 1 and 3. In some embodiments, the machine may beconnected (e.g., using a network 626) to other machines. In a networkeddeployment, the machine may operate in the capacity of a server or aclient user machine in a server-client user network environment, or as apeer machine in a peer-to-peer (or distributed) network environment.

The machine may comprise a server computer, a client user computer, apersonal computer (PC), a tablet, a smart phone, a laptop computer, adesktop computer, a control system, a network router, switch or bridge,or any machine capable of executing a set of instructions (sequential orotherwise) that specify actions to be taken by that machine. It will beunderstood that a communication device of the subject disclosureincludes broadly any electronic device that provides voice, video ordata communication. Further, while a single machine is illustrated, theterm “machine” shall also be taken to include any collection of machinesthat individually or jointly execute a set (or multiple sets) ofinstructions to perform any one or more of the methods discussed herein.

The computer system 600 may include a processor (or controller) 602(e.g., a central processing unit (CPU)), a graphics processing unit(GPU, or both), a main memory 604 and a static memory 606, whichcommunicate with each other via a bus 608. The computer system 600 mayfurther include a display unit 610 (e.g., a liquid crystal display(LCD), a flat panel, or a solid state display). The computer system 600may include an input device 612 (e.g., a keyboard), a cursor controldevice 614 (e.g., a mouse), a disk drive unit 616, a signal generationdevice 618 (e.g., a speaker or remote control) and a network interfacedevice 620. In distributed environments, the embodiments described inthe subject disclosure can be adapted to utilize multiple display units610 controlled by two or more computer systems 600. In thisconfiguration, presentations described by the subject disclosure may inpart be shown in a first of the display units 610, while the remainingportion is presented in a second of the display units 610.

The disk drive unit 616 may include a tangible computer-readable storagemedium 622 on which is stored one or more sets of instructions (e.g.,software 624) embodying any one or more of the methods or functionsdescribed herein, including those methods illustrated above. Theinstructions 624 may also reside, completely or at least partially,within the main memory 604, the static memory 606, and/or within theprocessor 602 during execution thereof by the computer system 600. Themain memory 604 and the processor 602 also may constitute tangiblecomputer-readable storage media.

Dedicated hardware implementations including, but not limited to,application specific integrated circuits, programmable logic arrays andother hardware devices can likewise be constructed to implement themethods described herein. Application specific integrated circuits andprogrammable logic array can use downloadable instructions for executingstate machines and/or circuit configurations to implement embodiments ofthe subject disclosure. Applications that may include the apparatus andsystems of various embodiments broadly include a variety of electronicand computer systems. Some embodiments implement functions in two ormore specific interconnected hardware modules or devices with relatedcontrol and data signals communicated between and through the modules,or as portions of an application-specific integrated circuit. Thus, theexample system is applicable to software, firmware, and hardwareimplementations.

In accordance with various embodiments of the subject disclosure, theoperations or methods described herein are intended for operation assoftware programs or instructions running on or executed by a computerprocessor or other computing device, and which may include other formsof instructions manifested as a state machine implemented with logiccomponents in an application specific integrated circuit or fieldprogrammable gate array. Furthermore, software implementations (e.g.,software programs, instructions, etc.) including, but not limited to,distributed processing or component/object distributed processing,parallel processing, or virtual machine processing can also beconstructed to implement the methods described herein. Distributedprocessing environments can include multiple processors in a singlemachine, single processors in multiple machines, and/or multipleprocessors in multiple machines. It is further noted that a computingdevice such as a processor, a controller, a state machine or othersuitable device for executing instructions to perform operations ormethods may perform such operations directly or indirectly by way of oneor more intermediate devices directed by the computing device.

While the tangible computer-readable storage medium 622 is shown in anexample embodiment to be a single medium, the term “tangiblecomputer-readable storage medium” should be taken to include a singlemedium or multiple media (e.g., a centralized or distributed database,and/or associated caches and servers) that store the one or more sets ofinstructions. The term “tangible computer-readable storage medium” shallalso be taken to include any non-transitory medium that is capable ofstoring or encoding a set of instructions for execution by the machineand that cause the machine to perform any one or more of the methods ofthe subject disclosure. The term “non-transitory” as in a non-transitorycomputer-readable storage includes without limitation memories, drives,devices and anything tangible but not a signal per se.

The term “tangible computer-readable storage medium” shall accordinglybe taken to include, but not be limited to: solid-state memories such asa memory card or other package that houses one or more read-only(non-volatile) memories, random access memories, or other re-writable(volatile) memories, a magneto-optical or optical medium such as a diskor tape, or other tangible media which can be used to store information.Accordingly, the disclosure is considered to include any one or more ofa tangible computer-readable storage medium, as listed herein andincluding art-recognized equivalents and successor media, in which thesoftware implementations herein are stored.

Although the present specification describes components and functionsimplemented in the embodiments with reference to particular standardsand protocols, the disclosure is not limited to such standards andprotocols. Each of the standards for Internet and other packet switchednetwork transmission (e.g., TCP/IP, UDP/IP, HTML, HTTP) representexamples of the state of the art. Such standards are from time-to-timesuperseded by faster or more efficient equivalents having essentiallythe same functions. Wireless standards for device detection (e.g.,RFID), short-range communications (e.g., Bluetooth®, WiFi, Zigbee), andlong-range communications (e.g., WiMAX, GSM, CDMA, LTE) can be used bycomputer system 600. In one or more embodiments, information regardinguse of services can be generated including services being accessed,media consumption history, user preferences, and so forth. Thisinformation can be obtained by various methods including user input,detecting types of communications (e.g., video content vs. audiocontent), analysis of content streams, and so forth. The generating,obtaining and/or monitoring of this information can be responsive to anauthorization provided by the user. In one or more embodiments, ananalysis of data can be subject to authorization from user(s) associatedwith the data, such as an opt-in, an opt-out, acknowledgementrequirements, notifications, selective authorization based on types ofdata, and so forth.

The illustrations of embodiments described herein are intended toprovide a general understanding of the structure of various embodiments,and they are not intended to serve as a complete description of all theelements and features of apparatus and systems that might make use ofthe structures described herein. Many other embodiments will be apparentto those of skill in the art upon reviewing the above description. Theexemplary embodiments can include combinations of features and/or stepsfrom multiple embodiments. Other embodiments may be utilized and derivedtherefrom, such that structural and logical substitutions and changesmay be made without departing from the scope of this disclosure. Figuresare also merely representational and may not be drawn to scale. Certainproportions thereof may be exaggerated, while others may be minimized.Accordingly, the specification and drawings are to be regarded in anillustrative rather than a restrictive sense.

Although specific embodiments have been illustrated and describedherein, it should be appreciated that any arrangement which achieves thesame or similar purpose may be substituted for the embodiments describedor shown by the subject disclosure. The subject disclosure is intendedto cover any and all adaptations or variations of various embodiments.Combinations of the above embodiments, and other embodiments notspecifically described herein, can be used in the subject disclosure.For instance, one or more features from one or more embodiments can becombined with one or more features of one or more other embodiments. Inone or more embodiments, features that are positively recited can alsobe negatively recited and excluded from the embodiment with or withoutreplacement by another structural and/or functional feature. The stepsor functions described with respect to the embodiments of the subjectdisclosure can be performed in any order. The steps or functionsdescribed with respect to the embodiments of the subject disclosure canbe performed alone or in combination with other steps or functions ofthe subject disclosure, as well as from other embodiments or from othersteps that have not been described in the subject disclosure. Further,more than or less than all of the features described with respect to anembodiment can also be utilized.

Less than all of the steps or functions described with respect to theexemplary processes or methods can also be performed in one or more ofthe exemplary embodiments. Further, the use of numerical terms todescribe a device, component, step or function, such as first, second,third, and so forth, is not intended to describe an order or functionunless expressly stated so. The use of the terms first, second, thirdand so forth, is generally to distinguish between devices, components,steps or functions unless expressly stated otherwise. Additionally, oneor more devices or components described with respect to the exemplaryembodiments can facilitate one or more functions, where the facilitating(e.g., facilitating access or facilitating establishing a connection)can include less than every step needed to perform the function or caninclude all of the steps needed to perform the function.

In one or more embodiments, a processor (which can include a controlleror circuit) has been described that performs various functions. Itshould be understood that the processor can be multiple processors,which can include distributed processors or parallel processors in asingle machine or multiple machines. The processor can be used insupporting a virtual processing environment. The virtual processingenvironment may support one or more virtual machines representingcomputers, servers, or other computing devices. In such virtualmachines, components such as microprocessors and storage devices may bevirtualized or logically represented. The processor can include a statemachine, application specific integrated circuit, and/or programmablegate array including a Field PGA. In one or more embodiments, when aprocessor executes instructions to perform “operations”, this caninclude the processor performing the operations directly and/orfacilitating, directing, or cooperating with another device or componentto perform the operations.

The Abstract of the Disclosure is provided with the understanding thatit will not be used to interpret or limit the scope or meaning of theclaims. In addition, in the foregoing Detailed Description, it can beseen that various features are grouped together in a single embodimentfor the purpose of streamlining the disclosure. This method ofdisclosure is not to be interpreted as reflecting an intention that theclaimed embodiments require more features than are expressly recited ineach claim. Rather, as the following claims reflect, inventive subjectmatter lies in less than all features of a single disclosed embodiment.Thus the following claims are hereby incorporated into the DetailedDescription, with each claim standing on its own as a separately claimedsubject matter.

What is claimed is:
 1. A method, comprising: sending, by a processingsystem including a processor of a mobile device, a transport protocolmessage to a server, wherein the transport protocol message enablesidentification of a codec; and based on the sending the transportprotocol message to the server, receiving, by the processing system ofthe mobile device and from a media resource function, a media service,wherein the media resource function is accessed by the server using anoperable resource identifier associated with the media resourcefunction, and wherein the server is configured to obtain the operableresource identifier by searching a codec table or by querying a domainname server.
 2. The method of claim 1, wherein the codec is determinedaccording to a media description.
 3. The method of claim 2, wherein themedia description is determined according to session descriptionprotocol information associated with the transport protocol message. 4.The method of claim 1, wherein the codec comprises hardware.
 5. Themethod of claim 1, wherein the codec comprises software.
 6. The methodof claim 1, wherein the operable resource identifier comprises a domainname.
 7. The method of claim 1, further comprising: requesting, by theprocessing system of the mobile device, a conference service subsequentto the receiving the media service, wherein another media resourcefunction provides the conference service to the mobile device responsiveto the requesting.
 8. The method of claim 7, wherein a second resourceidentifier associated with the another media resource function isdetermined by the server according to the codec table.
 9. The method ofclaim 1, wherein the transport protocol message relates to a callsession.
 10. The method of claim 9, wherein the call session comprises avoice-over-IP function.
 11. The method of claim 1, wherein the transportprotocol message relates to a video call.
 12. A non-transitory,machine-readable storage medium, comprising executable instructionsthat, when executed by a processing system including a processor,facilitate performance of operations, the operations comprising:providing a conference request to a server, wherein the conferencerequest enables identification of a codec; and based on the providingthe conference request, obtaining a media service from a media resourcefunction, wherein the server facilitates the obtaining by accessing themedia resource function using an operable resource identifier associatedwith the media resource function, and wherein the server is configuredto obtain the operable resource identifier by searching a codec table orby querying a domain name server.
 13. The non-transitory,machine-readable storage medium of claim 12, wherein the conferencerequest relates to a voice call or a video call.
 14. The non-transitory,machine-readable storage medium of claim 12, wherein the operableresource identifier comprises a fully qualified domain name.
 15. Thenon-transitory, machine-readable storage medium of claim 12, wherein theconference request comprises a session initiation protocol message. 16.The non-transitory, machine-readable storage medium of claim 12, whereinthe codec comprises software.
 17. A mobile device, comprising: aprocessing system including a processor; and a memory that storesexecutable instructions that, when executed by the processing system,facilitate performance of operations, the operations comprising:providing a transport protocol message to a server, wherein thetransport protocol message enables identification of a codec; and afterthe providing the transport protocol message, accessing a media servicefrom a media resource function, wherein the accessing is based on acommand from the server to the media resource function, wherein theserver accesses the media resource function using an operable resourceidentifier associated with the media resource function, and wherein theserver is configured to obtain the operable resource identifier bysearching a codec table or by querying a domain name server.
 18. Themobile device of claim 17, wherein the transport protocol message isassociated with a call session.
 19. The mobile device of claim 18,wherein the call session is related to a voice call or a video call. 20.The mobile device of claim 17, wherein the codec comprises hardware.